You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The ConcurrentLinkedQueue doesn't have a size limitation in Iceberg 1.6.0. When the iceberg table is large, the queue will also become really large, which will cause OOM in the FE.
As per the above screenshot, the ConcurrentLinkedQueue is consuming 91%+ of the heap memory and causing the Frontend (FE) to go down, this indicates a significant memory management issue due to unbounded growth of the queue.
This issue was resolved with Iceberg 1.6.1(#10691)
What I'm doing:
as title
What type of PR is this:
BugFix
Feature
Enhancement
Refactor
UT
Doc
Tool
Does this PR entail a change in behavior?
Yes, this PR will result in a change in behavior.
No, this PR will not result in a change in behavior.
If yes, please specify the type of change:
Interface/UI changes: syntax, type conversion, expression evaluation, display information
Parameter changes: default values, similar parameters but with different default values
Policy changes: use new policy to replace old one, functionality automatically enabled
Feature removed
Miscellaneous: upgrade & downgrade compatibility, etc.
Checklist:
I have added test cases for my bug fix or my new feature
This pr needs user documentation (for new or modified features or behaviors)
I have added documentation for my new feature or new function
This is a backport pr
Bugfix cherry-pick branch check:
I have checked the version labels which the pr will be auto-backported to the target branch
zhaohehuhu
changed the title
Upgrade Iceberg to 1.6.1 to limit memory used by ParallelIterable
[Enhancement] Upgrade Iceberg to 1.6.1 to limit memory used by ParallelIterable
Dec 23, 2024
zhaohehuhu
changed the title
[Enhancement] Upgrade Iceberg to 1.6.1 to limit memory used by ParallelIterable
[Enhancement] Limit memory used by ParallelIterable in Iceberg
Dec 27, 2024
how many manifest files and data files in your case? I think if you use version 3.3 or above, this case may go to distributed plan, not local plan.
Total Size of metadata is 439MB, while data files occupies 2TB space. Iceberg already released 1.6.1 to fix this issue, so it would be nice for us to update the version of Iceberg.
how many manifest files and data files in your case? I think if you use version 3.3 or above, this case may go to distributed plan, not local plan.
Total Size of metadata is 439MB, while data files occupies 2TB space. Iceberg already released 1.6.1 to fix this issue, so it would be nice for us to update the version of Iceberg.
could you try to set plan_mode=distributed then retry this query? you can observe if memory still high
how many manifest files and data files in your case? I think if you use version 3.3 or above, this case may go to distributed plan, not local plan.
Total Size of metadata is 439MB, while data files occupies 2TB space. Iceberg already released 1.6.1 to fix this issue, so it would be nice for us to update the version of Iceberg.
could you try to set plan_mode=distributed then retry this query? you can observe if memory still high
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
zhaohehuhu
changed the title
Why I'm doing:
The ConcurrentLinkedQueue doesn't have a size limitation in Iceberg 1.6.0. When the iceberg table is large, the queue will also become really large, which will cause OOM in the FE.
As per the above screenshot, the ConcurrentLinkedQueue is consuming 91%+ of the heap memory and causing the Frontend (FE) to go down, this indicates a significant memory management issue due to unbounded growth of the queue.
This issue was resolved with Iceberg 1.6.1(#10691)
What I'm doing:
as title
What type of PR is this:
Does this PR entail a change in behavior?
If yes, please specify the type of change:
Checklist:
Bugfix cherry-pick branch check: